Codecov Report

Attention: Patch coverage is 69.23077% with 12 lines in your changes missing coverage. Please review.

Project coverage is 36.46%. Comparing base (2ef6022) to head (60af466).
Report is 254 commits behind head on main.

@@            Coverage Diff             @@
##             main    #3965      +/-   ##
==========================================
- Coverage   40.10%   36.46%   -3.65%     
==========================================
  Files         155      209      +54     
  Lines       10044    13312    +3268     
==========================================
+ Hits         4028     4854     +826     
- Misses       5530     7839    +2309     
- Partials      486      619     +133     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

I'm a little -1 on this, as a change in conformance testing can cause builds to start failing (so we'd need to fix it right away or override branch protection). Dependabot PRs should already take care of the version bumps, and we can see the test failures before they land in main. Of course, releases only happen so often so it's nice to know about failures early...

Alternatively, we can have two conformance workflows, one with the latest pinned release and the second running against main, and only use branch protection on the pinned one so that branch protection is stable. What do you think of that?

aside: dependabot wasn't working here, because this was back pinned to v0.0.11 which was released in March...

I'm a little -1 on this, as a change in conformance testing can cause builds to start failing (so we'd need to fix it right away or override branch protection). Dependabot PRs should already take care of the version bumps, and we can see the test failures before they land in main. Of course, releases only happen so often so it's nice to know about failures early...

Alternatively, we can have two conformance workflows, one with the latest pinned release and the second running against main, and only use branch protection on the pinned one so that branch protection is stable. What do you think of that?

i'll downscope this change to just get to the latest release. I still vote +1 on this because if we have a valid conformance test that isn't passing on a client, then the client should be updated ASAP in my opinion (and block other changes/releases).